Systems and methods for online advertising using user preferences

ABSTRACT

Various implementations described herein provide systems and methods for online advertising and, more particularly, systems and methods that utilize user preferences in providing online advertising. In various implementations, systems or methods described herein facilitate user control of user-related data with respect to online advertisement systems, which can include supply-side platforms (SSPs), advertisement exchanges, demand-side platforms (DSPs), content delivery networks (CDNs), ad networks, or adservers. In some implementations, the system and methods implement or otherwise facilitate a user advertisement preference service that enables online users to manage one or more user advertisement preferences and selectively provide those user advertisement preferences to online advertisement systems.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/831,261 filed Dec. 4, 2017 and entitled “Systems and Methodsfor Online Advertising Using User Preferences,” which is a continuationof U.S. patent application Ser. No. 14/255,953 filed Apr. 17, 2014 andentitled “Systems and Methods for Online Advertising Using UserPreferences,” which claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/813,123 filed Apr. 17, 2013 and entitled “UserCentric Advertising Preferences Platform to Inject into the Ad EcoSystem,” which are hereby incorporated by reference herein.

BACKGROUND 1. Technical Field

Various embodiments of the present invention(s) relate to systems andmethods for online advertising and, more particularly, systems andmethods that utilize user preferences in providing online advertising.

2. Description of Related Art

Online Behavior Advertising (OBA) is a well-known practice by whichcompanies gather information about a user's online activity and use thatinformation to show that user ads that are relevant to the user. Cookiesare just one way in which companies can track what web pages users visitand user activity on such web pages (e.g., clicking onlineadvertisements, clicking web links, submitting searches, etc.). Cookiesand other types of trackers usually limit the information gathered togeneralized facts regarding the user (e.g., age group, gender, userinterests, etc.) and usually avoid gathering specific personalinformation (e.g., name, address, phone number, etc.). Nevertheless,given the importance of personal privacy in today's society,particularly with respect to information being gathered during onlineactivities, the ability for online users to control what (or what typeof) information is gather about them during online activities has neverbeen more important. Online advertisement blockers, disabling trackers(e.g., disabling cookies), and browser privacy settings (e.g., “Do NotTrack” options) are just some of the ways online users already exercisesuch control.

The foregoing examples of the related art and limitations relatedtherewith are intended to be illustrative and not exclusive. Otherlimitations of the relevant art will become apparent to those of skillin the art upon a reading of the specification and a study of thedrawings.

SUMMARY OF EMBODIMENTS

The following implementations and aspects thereof are described andillustrated in conjunction with systems, tools, and methods that aremeant to be exemplary and illustrative, not necessarily limiting inscope. In various implementations one or more of the above-describedproblems have been addressed, while other implementations are directedto other improvements.

Various implementations described herein provide systems and methods foronline advertising and, more particularly, systems and methods thatutilize user preferences in providing online advertising. In variousimplementations, systems or methods described herein facilitate usercontrol of user-related data with respect to online advertisementsystems, which can include supply-side platforms (SSPs), advertisementexchanges, demand-side platforms (DSPs), content delivery networks(CDNs), ad networks, or adservers.

In some implementations, the system and methods implement or otherwisefacilitate a user advertisement preference service that enables onlineusers to manage one or more user advertisement preferences andselectively provide those user advertisement preferences to onlineadvertisement systems. For some implementations, a user at a clientdevice can authenticate with the service and visit a website, whichresults in the service issuing a web browser cookie to the clientdevice. The web browser cookie can include a unique user identifier (ID)that is associated with the authenticated user. The web browser cookiecan also include one or more variables relating to the authenticateduser's advertisement preference, such a Boolean variable indicatingwhether the authenticated user has any saved user advertisementpreferences at the moment. For some implementations, when theauthenticated user at a client device visits a web page that includes arequest for online advertisement from online advertisement systems, theweb browser cookie is sent to the online advertisement systems as partof the request process. The online advertisement systems, in turn, canutilize the unique user ID contained in the web browser cookie to obtainone or more user advertisement preferences associated with theauthenticated user corresponding to the unique user ID. Depending on theimplementation, the service may or may not have pushed the useradvertisement preferences with its associated unique user ID to theonline advertisement system in advance of the request for the onlineadvertisement. In some implementations, the online advertisement systemsrequest one or more user advertisement preference from the service usingthe unique user ID.

For management of user advertisement preferences, the client device caninclude a client-side engine (e.g., accessed as a web browser plugin orthrough APIs) configured to provide access to user advertisementpreferences (e.g., through an icon included over or adjacent to eachonline advertisement presented in a web page). By accessing the useradvertisement preferences using the client-side engine, an authenticateduser can review, add, remove, or modify various user advertisementpreferences. The client-side engine may be further configured monitorfor online advertisements (e.g., those presented in a web page through aweb browser) and filter the user advertisement preferences presented foraccess to those relating to the online advertisement currentlydisplayed. The client-engine can detect the web browser cookie andutilize data contain therein, such as the unique user ID, to facilitatemanagement of user advertisement preferences for the authenticated user.For example, as the authenticated user interacts with user advertisementpreferences (e.g., create new preferences or modify existingpreferences) through the client-side engine (e.g., through a graphicuser interface provided by the client-side engine), the client-sideengine can communicate changes to the user advertisement preferences tothe user advertisement preference service (e.g., a server implementingthe service).

These and other advantages will become apparent to those skilled in therelevant art upon a reading of the following descriptions and a study ofthe several examples of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example environment thatincludes a user advertisement preference system in accordance with someimplementations.

FIG. 2 is a block diagram illustrating an example client device inaccordance with some implementations.

FIG. 3 is a block diagram illustrating an example client-side useradvertisement preference engine in accordance with some implementations.

FIG. 4 is a block diagram illustrating an example (server-side) useradvertisement preference system in accordance with some implementations.

FIG. 5 is flow diagram illustrating operation of an example useradvertisement preference system in accordance with some implementations.

FIG. 6 is a flowchart illustrating an example method for useradvertisement preferences in accordance with some implementations.

FIG. 7 is a flowchart illustrating an example method for useradvertisement preferences in accordance with some implementations.

FIG. 8 provides a screenshot of an example graphical user interface foraccessing user advertisement preferences in accordance with someimplementations.

FIG. 9 provides a screenshot of an example graphical user interface foraccessing user advertisement preferences in accordance with someimplementations.

FIGS. 10 and 11 provide screenshots of example graphical user interfacesfor accessing user advertisement preferences in accordance with someimplementations.

FIGS. 12 and 13 provide screenshots of example graphical user interfacesfor accessing and interacting with a user advertisement preferencesystem in accordance with some implementations.

The figures are not intended to be exhaustive or to limit theembodiments to the precise form disclosed. It should be understood thatvarious implementations may be practiced with modification andalteration.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various implementations described herein provide systems and methods foronline advertising and, more particularly, systems and methods thatutilize user preferences in providing online advertising. In variousimplementations, systems or methods described herein facilitate usercontrol of user-related data with respect to online advertisementsystems, which can include supply-side platforms (SSPs), advertisementexchanges, demand-side platforms (DSPs), content delivery networks(CDNs), ad networks, or adservers.

Depending on the implementation, the user can control whether an onlineadvertisement system receives user-related data, and what user-relateddata is provided to an online advertisement system. For someimplementations, the user-related data includes one or more preferencesa particular user has with respect to receiving online advertisements(hereafter, referred to as user advertisement preferences). By managingsuch user advertisement preferences (e.g., creating new preferences, orremoving or modifying existing preferences), a user can effectivelycontrol what user-related data provided to online advertisement systems.Additionally, use of such user advertisement preferences can benefitonline advertisement systems by providing them with richer user profilescontaining trusted, user-related data provided gathered directly fromonline users (in the form of user preferences). With richer userprofiles, online advertisement systems can better select and provideonline advertising that is relevant to online users, thereby optimizingthe selection and delivery process of online advertising, improvingadvertising quality, and improving return on investment (ROI).

In one implementation, a web browser user is sent an invitation tocreate an account with the user advertisement preferences service, andinstalls (at their client device) a web browser plug-in (e.g., add-on)configured to interact with the service and facilitate client-sideoperations. Once the web browser user has authenticated with the service(i.e., is an authenticated user), a subsequent visit to a website cancause the web browser plug-in to display one or more graphical userinterface (GUIs) elements, possibly on or near each online advertisementdisplayed in the website, to provide access to user advertisementpreferences. The GUI elements can include a menu bar (e.g., floating),visual overlays over the ads (e.g., small icon included in the corner ofeach online advertisement), a pop-up menu, and the like. For someimplementations, the GUI is provided through a separate web browserwindow, which may be invoked when access to user advertisementpreferences is appropriate.

Depending on the implementation, the icon may only display with respectto those online advertisement originating from an online advertisementnetwork affiliated with the user advertisement preferences service(e.g., those ad networks that are subscribed to and utilize the useradvertisement preferences service).

Each icon displayed can provide the authenticated user access to useradvertisement preferences related to a particular online advertisementbeing displayed on the website, or a group of online advertisementsbeing displayed on the website. When accessing the user advertisementpreferences, the authenticated user can add, remove, or modify useradvertisement preferences. For example, where a given onlineadvertisement relates to a motor vehicle, the user advertisementpreferences presented with respect to the given online advertisement caninclude one or more of the following kind of preference options: “Ialready bought a car”; “I just bought a car so no car ads for 2 years”;“I am not interested in cars”; “I am not interested by this car brand”;“I do not want to receive any targeted ads”; “Take My Ads PreferenceSettings Menu”; and “Share this Ad with a friend.” Based on the userselection of the preference option, the web browser plug-in can causethe user advertisement preference saved by the service to be updatedaccordingly.

In some implementations, when an authenticated user accesses a website,a window popup is displayed to provide a listing of onlineadvertisements including on the website. The listing may be according tobrand, product category, product, and the like. Through the windowpopup, the authenticated user can access user advertisement preferenceswith respect to the online advertisements, and select such preferenceoptions as: “I already bought such a product”; “I am not interested inthis product category”; “I am not interested by this brand”; “I am notinterested by this retailer”; “I do not want to receive any targetedads”; and the like.

In various implementations, where a non-authenticated user attempts toaccess user advertisement preferences (e.g., an icon shown on an onlineadvertisement), the user can be directed to sign-up to the useradvertisement service and invited to install the web browser plug-in. Insome implementations, until the web brown plug-in is installed, a usermay not access user advertisement preferences options or such optionsare shown to be disabled (e.g., when the user clicks on an iconassociated with the user advertisement preference service that isincluded with the display of an online advertisement).

FIG. 1 is a block diagram 100 illustrating an example environment thatincludes a user advertisement preference system 102 in accordance withsome implementations. In particular implementations, the useradvertisement preference system 102 depicted in FIG. 1 facilitates auser advertisement preference service whereby a user can provide one ormore user advertisement preferences to the service and the service canprovide those preferences to online advertisement systems. The examplesystem shown in FIG. 1 includes a user advertisement preference system102, one or more online advertisement systems 104-1 thru 104-Nhereafter, collectively referred to as the online advertisement systems104), a computer-readable medium 106, a web servers 108-1 thru 108-N(hereafter, collectively referred to as the web servers 108), and one ormore client devices 110-1 thru 110-N (hereafter, collectively referredto as the client devices 110). As shown in FIG. 1, each of the useradvertisement preference system 102, the online advertisement systems104, the web servers 108, and the client devices 110 are communicativelycoupled through the computer-readable medium 106.

As used in this paper, a computer-readable medium is intended to includeall mediums that are statutory (e.g., in the United States, under 35U.S.C. 101), and to specifically exclude all mediums that arenon-statutory in nature to the extent that the exclusion is necessaryfor a claim that includes the computer-readable medium to be valid.Known statutory computer-readable mediums include hardware (e.g.,registers, random access memory (RAM), non-volatile (NV) storage, toname a few), but may or may not be limited to hardware.

In the example of FIG. 1, the computer-readable medium 106 can representa bus or other memory device on a computer that includes one or more ofthe other components illustrated as coupled to the computer-readablemedium 106 in the example of FIG. 1. Where the computer-readable medium106 includes more than one computing device, the computer-readablemedium 106 would typically be characterized as including a “network.”The computer-readable medium 106 can include wired and wirelessnetworks. In a wired communications context, the computer-readablemedium 106 can include a wired network, such as a local area network(LAN) or wide area network (WAN). In a wireless communications context,the computer-readable medium 104 can include a wireless LAN (WLAN).

Assuming the computer-readable medium 106 includes a network, thenetwork can be practically any type of communications network, such asthe Internet or an infrastructure network. The term “Internet” as usedin this paper refers to a network of networks that use certainprotocols, such as the TCP/IP protocol, and possibly other protocols,such as the hypertext transfer protocol (HTTP) for hypertext markuplanguage (HTML) documents that make up the World Wide Web (“the web”).More generally, the network 106 can include, for example, a WAN,metropolitan area network (MAN), campus area network (CAN), or LAN, butthe network 106 could at least theoretically be of any size orcharacterized in some other fashion (e.g., personal area network (PAN)or home area network (HAN), to name a couple of alternatives). Networkscan include enterprise private networks and virtual private networks(collectively, private networks). As the name suggests, private networksare under the control of a single entity. Private networks can include ahead office or headquarters and optional branch or regional offices(collectively, offices). Many offices enable remote users to connect tothe private network offices via some other network, such as theInternet. The example of FIG. 1 is intended to illustrate acomputer-readable medium 106 that may or may not include more than oneprivate network.

The user advertisement preference system 102, the online advertisementsystems 104, the web servers 108, the client devices 110, and othersystems or devices described in this paper, can be implemented by one ormore a computer systems or as part of one or more computer systems. Acomputer system, as used in this paper, is intended to be construedbroadly and can include or be implemented as a specific purpose computersystem for carrying out the functionalities described in this paper. Ingeneral, a computer system will include a processor, memory,non-volatile storage, and an interface. A typical computer system willusually include at least a processor, memory, and a device (e.g., a bus)coupling the memory to the processor. The processor can be, for example,a general-purpose central processing unit (CPU), such as amicroprocessor, or a special-purpose processor, such as amicrocontroller.

The memory can include, by way of example but not limitation, randomaccess memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM).The memory can be local, remote, or distributed. The bus can also couplethe processor to non-volatile storage. The non-volatile storage is oftena magnetic floppy or hard disk, a magnetic-optical disk, an opticaldisk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, amagnetic or optical card, or another form of storage for large amountsof data. Some of this data is often written, by a direct memory accessprocess, into memory during execution of software on the computersystem. The non-volatile storage can be local, remote, or distributed.The non-volatile storage is optional because systems can be created withall applicable data available in memory.

Software is typically stored in the non-volatile storage. Indeed, forlarge programs, it may not even be possible to store the entire programin the memory. Nevertheless, it should be understood that for softwareto run, if necessary, it is moved to a computer-readable locationappropriate for processing, and for illustrative purposes, that locationis referred to as the memory in this paper. Even when software is movedto the memory for execution, the processor will typically make use ofhardware registers to store values associated with the software, andlocal cache that, ideally, serves to speed up execution. As used herein,a software program is assumed to be stored at an applicable known orconvenient location (from non-volatile storage to hardware registers)when the software program is referred to as “implemented in acomputer-readable storage medium.” A processor is considered to be“configured to execute a program” when at least one value associatedwith the program is stored in a register readable by the processor.

In one example of operation, a computer system can be controlled byoperating system software, which is a software program that includes afile management system, such as a disk operating system. One example ofoperating system software with associated file management systemsoftware is the family of operating systems known as Windows® fromMicrosoft Corporation of Redmond, Wash., and their associated filemanagement systems. Another example of operating system software withits associated file management system software is the Linux operatingsystem and its associated file management system. The file managementsystem is typically stored in the non-volatile storage and causes theprocessor to execute the various acts required by the operating systemto input and output data and to store data in the memory, includingstoring files on the non-volatile storage.

The bus can also couple the processor to the interface. The interfacecan include one or more input and/or output (I/O) devices. The I/Odevices can include, by way of example but not limitation, a keyboard, amouse or other pointing device, disk drives, printers, a scanner, andother I/O devices, including a display device. The display device caninclude, by way of example but not limitation, a cathode ray tube (CRT),liquid crystal display (LCD), or some other applicable known orconvenient display device. The interface can include one or more of amodem or network interface. It will be appreciated that a modem ornetwork interface can be considered to be part of the computer system.The interface can include an analog modem, ISDN modem, cable modem,token ring interface, satellite transmission interface (e.g. “directPC”), or other interfaces for coupling a computer system to othercomputer systems. Interfaces enable computer systems and other devicesto be coupled together in a network.

The computer systems can be compatible with or implemented as part of orthrough a cloud-based computing system. As used in this paper, acloud-based computing system is a system that provides virtualizedcomputing resources, software and/or information to client devices. Thecomputing resources, software and/or information can be virtualized bymaintaining centralized services and resources that the edge devices canaccess over a communication interface, such as a network. “Cloud” may bea marketing term and for the purposes of this paper can include any ofthe networks described herein. The cloud-based computing system caninvolve a subscription for services or use a utility pricing model.Users can access the protocols of the cloud-based computing systemthrough a web browser or other container application located on theirclient device.

A computer system can be implemented as an engine, as part of an engineor through multiple engines. As used in this paper, an engine includesat least two components: 1) a dedicated or shared processor and 2)hardware, firmware, and/or software modules that are executed by theprocessor. Depending upon implementation-specific, configurationspecific, or other considerations, an engine can be centralized or itsfunctionality distributed. An engine can be a specific purpose enginethat includes specific purpose hardware, firmware, or software embodiedin a computer-readable medium for execution by the processor. Theprocessor transforms data into new data using implemented datastructures and methods, such as is described with reference to the FIGs.in this paper.

The engines described in this paper, or the engines through which thesystems and devices described in this paper can be implemented, can becloud-based engines. As used in this paper, a cloud-based engine is anengine that can run applications and/or functionalities using acloud-based computing system. All or portions of the applications and/orfunctionalities can be distributed across multiple computing devices,and need not be restricted to only one computing device. In someembodiments, the cloud-based engines can execute functionalities and/ormodules that end users access through a web browser or containerapplication without having the functionalities and/or modules installedlocally on the end-users' computing devices.

In the example shown in FIG. 1, the user advertisement preference system102 is coupled to the computer-readable medium 106, through which theuser advertisement preference system 102 can communicate with one ormore of the online advertisement systems 104, the web servers 108, andthe client devices 110. Depending on the implementation, the useradvertisement preference system 102 can be implemented as part of anonline advertisement network or can be implemented as a serviceaffiliated with other online advertisement services (e.g., thatselection, place or deliver online advertisements).

In some implementations, the user advertisement preference system 102 isconfigured to authenticate a web browser user located at one of theclient devices 110 (e.g., the client device 110-1). As used herein, anauthenticated web browser user (or authenticated user) is considered aweb browser user that has been successfully authenticated. Uponsuccessful authentication, the user advertisement preference system 102can provide the client device (e.g., the client device 110-1) with a webbrowser cookie including a unique user identifier associated with theauthenticated web browser user. Additionally, the user advertisementpreference system 102 can receive from the client device (e.g., theclient device 110-1) a user advertisement preference associated with theauthenticated web browser user. The user advertisement preferencereceive can be one that is newly created or can be an existing one thathas been modified. Upon receiving the user advertisement preference fromthe client device, the user advertisement preference system 102 canstore the user advertisement preference and may do so in associationwith the unique user identified associated with authenticated webbrowser user. In this way, when one of the online advertisement systems104 receives a given unique user identifier (e.g., by way of a webbrowser cookie) and intends to obtain user advertisement preferencesassociated with a web browser user associated with a given web browseruser, the given unique user identifier can be utilized to obtain theuser advertisement preferences from the user advertisement preferencesystem 102. Depending on the implementation, the user advertisementpreference system 102 may provide user advertisement preferences to oneor more of the online advertisement systems 104 by pushing useradvertisement preferences to the online advertisement systems 104 asuser advertisement preferences are created or modified. This push ofuser advertisement preferences can occur in advance of the onlineadvertisement systems 104 receiving request for online advertisementswith a web browser cookie containing a unique user ID. In someimplementations, the user advertisement preference system 102 providesuser advertisement preferences to one or more of the onlineadvertisement systems 104 based on specific requests from the onlineadvertisement systems 104. For example, when the online advertisementsystems 104-2 has received a request for online advertisement from theclient device 104-2 and the request has an associated web browser cookiecontaining a specific unique user ID, the online advertisement systems104-2 can send a request to the user advertisement preference system 102for user advertisement preferences associated with the specific uniqueuser ID (which the user advertisement preference system 102 may thenprovide the online advertisement systems 104-2).

In the example shown in FIG. 1, the online advertisement systems 104 arecoupled to the computer-readable medium 106, through which each of theonline advertisement systems 104 can communicate with one or more of theuser advertisement preference system 102, the web servers 108, and theclient devices 110. Depending on the implementation, the onlineadvertisement systems 104 can include supply-side platforms (SSPs),advertisement exchanges, demand-side platforms (DSPs), content deliverynetworks (CDNs), ad networks, or adservers (e.g., publisher adserversand marketer adservers). In some implementations, one or more of theonline advertisement systems 104 are configured to receive one or morerequests for online advertisements (e.g., from web browsers at one ormore of the client devices 110), select one or more onlineadvertisements based on the request, and provide the selected onlineadvertisements (e.g., to the one or more of the client devices 110). Therequests for the online advertisements can include those made by clientdevices based on code included in a web page (e.g., HTML, code includingan advertisement tag) and can also include those made by applications(e.g., mobile game and application) that utilize third-party onlineadvertisement services to obtain online advertisement impressions.

In the example shown in FIG. 1, the web servers 108 are coupled to thecomputer-readable medium 106, through which each of the web servers 108can communicate with one or more of the user advertisement preferencesystem 102, the online advertisement systems 104, and the client devices110. In some implementations, the web servers 108 are configured toserve web pages to one or more of the client devices 110, which may ormay not be access such web pages through a web browser or otherweb-based application (e.g., Spotify®). The web pages served by the webservers 108 can include those containing references or code tothird-party online advertisement services, which may be implemented byone or more of the online advertisement systems 104. Such references orcode can cause one or more of the online advertisement systems 104 toreceive a web browser cookie containing a unique user ID associated witha particular web browser user. As described herein, one or more of theonline advertisement systems 104 can use the unique user ID to obtainone or more user advertisement preferences from the user advertisementpreference system 102.

In the example shown in FIG. 1, the client devices 110 are coupled tothe remote gateway device 106, through which each of the client devices110 communicate with one or more of the user advertisement preferencesystem 102, the online advertisement systems 104, and the web servers108. Depending upon the specific implementation, one or more of theclient devices 110 can be: a mobile device, such as a smart phone,personal digital assistant (PDA), or wearable electronic device; asemi-mobile device, such as a notebook or laptop computer, or otherdevice that is generally considered portable; or a device generally notconsidered to be mobile, such as a desktop computer. Additionally, forsome implementations, one or more of the client devices 110 are a thinclient device or an ultra-thin client device.

In the example shown in FIG. 1, one or more of the client devices 110can include a web browser, or similar application, that enables a givenclient device to request and then receive a web page, or similar webcontent, from one or more of the web servers 108. The web page (orsimilar web content) can contain a reference or code that causes therequest of one or more online advertisements from one or more of theonline advertisement systems 104. It will be understood that a web pagecan include any web content that utilizes, references, or otherwisecauses the request of an online advertisement from an onlineadvertisement system.

In some implementations, a web browser user at least one of the clientdevices 110 (e.g., the client device 110-1) is authenticated by the useradvertisement preference system 102. The authentication can befacilitated at the client device (e.g., the client device 110-1) by waya client-side engine, such as a web browser plug-in, installed at theclient device. Once authenticated, the client device (e.g., the clientdevice 110-1) can receive a web browser cookie from the useradvertisement preference system 102, where the web browser cookieincludes a unique user identifier associated with the authenticated webbrowser user. This web browser cookie can be stored at the client device(e.g., the client device 110-1) and subsequently used in connection withrequests for requests for online advertisements (e.g., ads included inweb pages) to the online advertisement systems 104. For example, a webbrowser at the client device (e.g., the client device 110-1) can requestand receive a web page from one of the web servers 108, and subsequentlymake one or more requests, based on the code included in the web page,for online advertisements from one or more of the online advertisementsystems 104. When requests for the online advertisements are made, theclient device (e.g., the client device 110-1) can provide one or more ofthe online advertisement systems 104 with the web browser cookieobtained from the user advertisement preference system 102. In responseto the one or more requests, the client device (e.g., the client device110-1) can receive one or more online advertisements that were selectedby the one or more of the online advertisement systems 104 using useradvertisement preferences associated with the unique user ID included inthe web browser cookie. As described herein, once one of the onlineadvertisement systems 104 has received the web browser cookie, it canuse the unique user ID to access user advertisement preferencesassociated with unique user ID (and therefore the authenticated webbrowser user).

In some implementations, one or more of the client devices 110 include aclient-side engine that facilitate access to user advertisementpreferences stored at the user advertisement preference system 102 inconnection with web browser users. The client-side engine of a givenclient device (e.g., the client device 110-1) can be configured tomonitor online advertisements received and displayed at the clientdevice and provide access to user advertisement preferences based on theonline advertisements displayed. For some implementations, the useradvertisement preferences are limited to those online advertisementsoriginating from online advertisement providers affiliated with the useradvertisement preference system 102 (e.g., partnered with or subscribedto the service provided by the user advertisement preference system102). For some implementations, online advertisements originating fromonline advertisement providers that utilize one or more servicesprovided by the user advertisement preference system 102 include a smallicon (e.g., GIF) in the online advertisements. Through such an icon, aweb browser user at a client device (e.g., the client device 110-1) canclick on the icon and access user advertisement preferences relating tothe online advertisement over which the icon is displayed.

FIG. 2 is a block diagram 200 illustrating an example client device 202in accordance with some implementations. The example device 202 shown inFIG. 2 includes a web browser engine 204, a client-side useradvertisement preference engine 206, and a client-side web browsercookie datastore 208. The web browser 204 can include a web browser(e.g., Firefox®, Internet Explorer®, etc.) or any application thatutilizes web-based content. A web browser user at the client device 202can instruct the web browser to visit a website, which can result in aweb page being received by the client device 202. The web browser 204can display the web page by requesting and receiving external contentreferenced in the web page, including images and online advertisements.A given web page can include one or more online advertisement slotsavailable for filling with an online advertisement. In order tofacilitate the filling process, the web page can reference (e.g.,include online advertisement tags) to online advertising systems (e.g.,publisher adservers, SSPs, etc.) that can provide an onlineadvertisement for the slot. As the web browser requests and display webpages, web browser cookies received at the client device 202 can bestored in (and later retrieved from) the client-side web browser cookiedatastore 208. The client-side user advertisement preference engine 206can be configured to perform one or more operations at the client device202 relating to the user advertisement preference service describedherein. More regarding the client-side user advertisement preferenceengine 206 is discussed with respect to FIG. 3.

FIG. 3 is a block diagram 300 illustrating an example client-side useradvertisement preference engine 302 in accordance with someimplementations. The example engine 302 shown in FIG. 3 includes aclient-side user authentication engine 304, a client-side web browsercookie engine 306, a client-side user advertisement preferencecommunication engine 308, a user advertisement preference graphical userinterface (GUI) engine 310, a user advertisement preference editingengine 312, an advertisement monitoring engine 314, an advertisementanalysis engine 316, and a client-side user advertisement preferencedatastore 318.

In the example shown in FIG. 3, the client-side user authenticationengine 304 can be configured to facilitate authentication of a webbrowser user at a client device with a user advertisement system. Theclient-side web browser cookie engine 306 can be configured to receive aweb browser cookie from the user advertisement preference system andstore the web browser cookie at the client device (e.g., in theclient-side user advertisement preference datastore 318, or in the webcache of a web browser). The client-side user advertisement preferencecommunication engine 308 can be configured to communicate one or morenewly created or modified user advertisements preferences from theclient device (e.g., stored on the client-side user advertisementpreference datastore 318) to the user advertisement preference system.The user advertisement preference graphical user interface (GUI) engine310 can be configured to provide a GUI at the client device that canfacilitate access to one or more user advertisement preferences by a webbrowser user at the client device, and that can facilitate access to oneor more features of the user advertisement system (e.g., web browseruser authentication, user settings, etc.). While accessing the useradvertisement preference through a GUI, a web browser can provide userinputs to the GUI that result in the addition, removal, or modificationof a user advertisement preference. The user advertisement preferenceediting engine 312 can be configured to facilitate adding, removing, ormodifying a user advertisement preference. A GUI provided by the useradvertisement preference GUI engine 310 can facilitate a web browseruser's access to the features and functionality of the useradvertisement preference editing engine 312. The advertisementmonitoring engine 314 can be configured to monitor and detect onlineadvertisements displayed in a web page, cause the advertisement analysisengine 316 to analyze the characteristics of the displayed onlineadvertisements, and present a filtered list of user advertisementpreferences relating to the displayed online advertisements. Theclient-side user advertisement preference datastore 318 can beconfigured to data utilized by the various components of the client-sideuser advertisement preference engine 302, including user advertisementpreferences saved on a user advertisement preference system and providedto the client device for review by the web browser user. The data canalso include user advertisement preferences newly created at the clientdevice, and those user advertisement preferences modified at the clientdevice.

FIG. 4 is a block diagram 400 illustrating an example (server-side) useradvertisement preference system 402 in accordance with someimplementations. The example system 402 shown in FIG. 4 includes aserver-side user authentication engine 404, a web browser cookiemanagement engine 406, a server-side user advertisement preferencecommunication engine 408, a user advertisement preference managementengine 410, a user advertisement preference retrieval engine 412, a useradvertisement preference formatting engine 414, a user advertisementauthorization engine 416, a server-side web browser cookie datastore418, and a server-side user advertisement preference datastore 420.

In the example shown in FIG. 4, the server-side user authenticationengine 404 can be configured to facilitate authentication of a webbrowser user at a client device with the user advertisement system 402.The web browser cookie management engine 406 can be configured tofacilitate the creation and provisioning of web browser cookies, whichcan include generation of unique user IDs for web browser users andgeneration of other cookie data included in web browser cookies. Oncegenerated, the web browser cookie management engine 406 can issue theweb browser cookie to a client device, and can be store the issued webbrowser cookie on the server-side web browser cookie datastore 418. Theserver-side user advertisement preference communication engine 408 canbe configured to receive a client device one or more user advertisementspreferences that newly created or modified at the client device. Theuser advertisement preference management engine 410 can be configured tomanage adding, removing, and modifying (e.g., updating) useradvertisement preferences stored at the user advertisement system 402.The server-side user advertisement preference datastore 420 may or maynot be utilized at the user advertisement system 402 for storing added,removed, and modified user advertisement preferences. The useradvertisement preference retrieval engine 412 can be configured toretrieve one or more user advertisement preferences associated with aunique user ID, and providing those user advertisement preferences to anonline advertisement system (e.g., through the server-side useradvertisement preference communication engine 408). The useradvertisement preference formatting engine 414 can be configured todetermine a format for providing one or more user advertisementpreferences to an online advertisement system, and can be furtherconfigured to apply the determined format before the user advertisementpreferences are sent to the online advertisement. The user advertisementauthorization engine 416 can be configured to request permission from aweb browser user (e.g., at a client device) before one or more useradvertisement preferences are provided to an online advertisementsystem.

FIG. 5 is flow diagram 500 illustrating operation of an example useradvertisement preference system 512 in accordance with someimplementations. FIG. 5 includes a publisher's website 502, asupply-side platform (SSP) and ad exchange 504 (hereafter, the SSP 504),a client device 506, a publisher's adserver 508, a marketer's adserver510, the user advertisement preference system 512, and one or moredemand-side platforms (DSPs) 514. As illustrated in FIG. 5, a webbrowser user at the client device 506 can request authentication (A) andonce authenticated, the client device 506 can receive a web browsercookie (B) including a unique user ID associated with the authenticatedweb browser user. Subsequently, when the web browser user at the clientdevice 506 visits (C) a website served by the publisher's website 502,the client device 506 can receive a web page (D) of the website. Basedon code included in the web page (e.g., an online advertisement tag),the client device 506 can request (E) an online advertisement from thepublisher's adserver 508 for an online advertisement slot (hereafter, adslot) available on the web page to be displayed on the client device506. The publisher's adserver 508 in turn can send the client device 506a redirect (e.g., an online advertisement tag) (F) to the SSP 504 forobtaining the online advertisement for the available ad slot. Based onthe redirect from the publisher's adserver 508, the client device 506can send a request (G) for an online advertisement from the SSP 504.

In response to the request from the client device 506, the SSP 504 canestablish a real-time based (RTB) auction for ad slot available on theweb page. In some implementations, the client device 506 can provide theSSP 504 with the web browser cookie, and the SSP 504 can use the uniqueuser ID contained therein to request (H) and then receive (I) one ormore user advertisement preferences (associated with the unique user IDand, thus, also associated the authenticated web browser user) from theuser advertisement preference system 512. It will be understood that theweb browser cookie received from the client device 506 and containingthe unique user ID is different from any SSP cookie or DSP cookie thatthe client device 506 may or may not provide to the SSP 504. Using theuser advertisement preferences (e.g., products, brands, retailers,services, product/service categories, etc.) obtained (I) from the useradvertisement preference system 512, the SSP 504 can better price the adslot available on the web page. Depending on the implementation, wherethe client device 506 provides the SSP 504 with both the web browsercookie and the SSP cookie, the SSP 504 may utilize only the web browsercookie (and the associated user advertisement preferences) in pricingthe ad slot, or utilize information provided by both the useradvertisement preferences and the SSP cookie.

Once the auction for the ad slot, the SSP 504 can inform (J) one or moreof the DSPs 514 of the auction and opens the option for bidding by theDSPs 514. While informing (J) the DSPs 514 of the auction, the SSP 504can provide one or more of the DSPs 514 with the web browser cookie theSSP 504 obtained from the client device 504. Like the SSP 504, one ormore of the DSPs 514 can use the unique user ID contained in the webbrowser cookie to request (K) and receive (L) one or more useradvertisement preferences (associated with the unique user ID and, thus,also associated the authenticated web browser user) from the useradvertisement preference system 512. Using the user advertisementpreferences (e.g., products, brands, retailers, services,product/service categories, etc.) obtained (L) from the useradvertisement preference system 512, one or more of the DSPs 514 canmake more informed bids (M) on the ad slot available on the web page.The DSPs 514 can also utilize the user advertisement preferences in itsprocess of selecting an online advertisement to fill the ad slotavailable on the web page.

Eventually, the SSP 504 can determine the winning bid and send theclient device 506 a redirect (e.g., online advertisement tag) (N) to thewinning DSP (e.g., the DSP 514-1). In response, the client device 506can send a request (O) for online advertisement to the winning DSP(e.g., the DSP 514-1) and the winning DSP can respond (P) to the clientdevice 506 with a redirect (e.g., online advertisement tag) to themarketer's adserver 510. The client device 506 can request (Q) an onlineadvertisement from the marketer's adserver 510, which can provide theclient device 506 with an online advertisement (R) to fill the slot.Those skilled in the art will appreciate variations in this process mayexist in some implementations.

FIG. 6 is a flowchart 600 illustrating an example method for useradvertisement preferences in accordance with some implementations. Themethod illustrated by the flowchart 600 can be performed, in whole or inpart, on a client device in accordance with some implementations. Forsome implementations, the method illustrated by the flowchart 600implements client-side functionality as described herein. The flowchart600 is presented as a series of modules, but, in some implementations,the modules of the flowchart 600 can be reordered to a permutation ofthe illustrated order of modules or reorganized for parallel execution.The example flowchart 600 shown in FIG. 6 begins at module 602 with aweb browser user being authenticated by a user advertisement preferencesystem described herein. The web browser user can be one located at aclient device, and authentication using the user advertisementpreference system can be facilitated using a client-side engine (e.g.,web browser plug-in) included at the client device.

The example flowchart 600 shown in FIG. 6 continues to module 604 with aweb browser cookie being received from a user advertisement preferencesystem. The web browser cookie can include a unique user ID that isassociated with a web browser user successfully authenticated at module602. The web browser cookie can also include one or more other variablesrelating to user advertisement preferences, such as a name-value pairindicating the presence of one or more saved user advertisementpreferences on the user advertisement preference system.

The example flowchart 600 shown in FIG. 6 continues to module 606 withthe web browser cookie being stored. The web browser cookie can be theone received at module 604, and the web browser cookie can be stored ata datastore local to the client device. In some implementations, the webbrowser cookie is stored as part of the web browser cache.

The example flowchart 600 shown in FIG. 6 continues to module 608 wherea user input being is received, from the web browser user, with respectto a user advertisement preference. For example, a web browser user at aclient device may provide one or more user inputs that cause thecreation of a new user advertisement preference or a modification to anexisting user advertisement preference. The example flowchart 600 shownin FIG. 6 continues to module 610 where the user advertisementpreference, as determined (e.g., created or modified) by the user inputat module 608, is provided to the user advertisement preference system.

The example flowchart 600 shown in FIG. 6 continues to module 612 wherea web page is received, where the web page includes (e.g., HTML orJavaScript code for) an request for online advertisement from an onlineadvertisement system. The example flowchart 600 shown in FIG. 6continues to module 614 where the request for the online advertisementis sent to the online advertisement system. The example flowchart 600shown in FIG. 6 continues to module 616 where the web browser cookie,including the unique user ID associated with the authenticated webbrowser user, is provided to the online advertisement system.

The example flowchart 600 shown in FIG. 6 continues to module 618 wherean online advertisement is received from the online advertisementsystem, where the online advertisement is selected based on the useradvertisement preference. For some implementations, the useradvertisement preference, used by the online advertisement system inselecting the online advertisement, is obtained by the onlineadvertisement system from a user advertisement preference system usingthe unique user ID provided in the web browser cookie at module 616.

The example flowchart 600 shown in FIG. 6 continues to module 620 wherethe web page and the online advertisement, received at module 612, aredisplayed (e.g., through a web browser at the client device).

FIG. 7 is a flowchart 700 illustrating an example method for useradvertisement preferences in accordance with some implementations. Themethod illustrated by the flowchart 700 can be performed, in whole or inpart, on a server in accordance with some implementations. For someimplementations, the method illustrated by the flowchart 700 implementsserver-side functionality as described herein. The flowchart 700 ispresented as a series of modules, but, in some implementations, themodules of the flowchart 700 can be reordered to a permutation of theillustrated order of modules or reorganized for parallel execution. Theexample flowchart 700 shown in FIG. 7 begins at module 702 with a webbrowser user being authenticated by a user advertisement preferencesystem described herein. The web browser user can be one located at aclient device, and authentication using the user advertisementpreference system can be facilitated using a client-side engine (e.g.,web browser plug-in) included at the client device.

The example flowchart 700 shown in FIG. 7 continues to module 704 with aweb browser cookie being provided to a client device. The web browsercookie can include a unique user ID that is associated with a webbrowser user successfully authenticated at module 702. The web browsercookie can also include one or more other variables relating to useradvertisement preferences, such as a name-value pair indicating thepresence of one or more saved user advertisement preferences on the useradvertisement preference system.

The example flowchart 700 shown in FIG. 7 continues to module 706 with auser advertisement preference, associated with a web browser user, beingreceived from a client device. The user advertisement preferencereceived can be one newly created at the client device, or an existingone modified at the client device. The example flowchart 700 shown inFIG. 7 continues to module 708 with the user advertisement preferencereceived at module 706 being stored at a user advertisement preferencesystem. Where the user advertisement preference received at module 706is a modification to an existing preference, the storing of the useradvertisement preference at module 708 can comprise updating the useradvertisement preference as saved at the user advertisement preferencesystem.

The example flowchart 700 shown in FIG. 7 continues to module 710 wherea format is determined for providing the user advertisement preferenceto an online advertisement system. In some implementations, the formatcomprises a set of user advertisement preferences (e.g., array) and aunique user ID associated with the user advertisement preferences.

The example flowchart 700 shown in FIG. 7 continues to module 712 with auser advertisement system requesting permission, from a web browseruser, before providing the user advertisement preference. Depending onthe implementations, the request can be sent to the web browser userthrough an electronic message (e.g., SMS, e-mail, instance message,etc.) or through a request that is pushed to and presented through aclient-side engine residing at the client device at which the webbrowser user is currently authenticated.

The example flowchart 700 shown in FIG. 7 continues to module 714 with auser advertisement preference system providing the user advertisementpreference to an online advertisement system. Depending on theimplementation, the user advertisement preference can be provided to theonline advertisement system by the user advertisement preference systempushing the user advertisement preference (e.g., at or near real-time aspreferences are created or changed) or can be provided when the onlineadvertisement system request the user advertisement preference (e.g.,request based on unique user ID).

FIG. 8 provides a screenshot 800 of an example graphical user interfacefor accessing user advertisement preferences in accordance with someimplementations. As illustrated in FIG. 8, the web page includes onlineadvertisements 804 and each of the online advertisements 804 includes anicon (collectively referred to as the icons 802 disposed in the corner.As described herein, the icons 802 can be included when the onlineadvertisements 804 originate from an online advertisement system (e.g.,ad network) affiliated with (e.g., subscribed to) a user advertisementpreference service as described herein. Additionally, the icons 802 canbe included by a web browser plug-in that is included at a client deviceand configured to detect when online advertisements are displayed on aweb page. For some implementations, each of the icons 804 providesaccess to user advertisement preferences in connection with theirrespective online advertisement. This is illustrated in FIG. 9, whichprovides a screenshot 900 of an example graphical user interface foraccessing user advertisement preferences in accordance with someimplementations. As shown in FIG. 9, when an icon 902 is selected by aweb browser user authenticated at a client device, the web browser usercan be presented with a graphical user interface (GUI) 904 listingpossible user advertisement preference options the web browser user canselect.

FIGS. 10 and 11 provide screenshots of example graphical user interfaces1000 and 1100 for accessing user advertisement preferences in accordancewith some implementations. In some implementations, the graphicalinterfaces 1000 and 1100 are presented at a client device by aclient-side engine when the client-side engine detects onlineadvertisements on a web page and determines a listing of useradvertisement preferences related to the detected online advertisements.As shown in FIG. 10, the graphical user interfaces 1000 a and 1000 billustrate different selections by a web browser user with respect touser advertisement preferences relating to cars, hotels, foods, andshoes. Likewise, in FIG. 11, the graphical user interfaces 1100 a and1100 b, also illustrate different selections by a web browser user withrespect to user advertisement preferences relating to cars, hotels,foods, and shoes. Unlike the graphical user interfaces 1000 a and 1000b, the graphical user interfaces 1100 a and 1100 b allow a web browseruser to select, as user advertisement preferences, which of productcategories (e.g., cars, hotels, foods, and shoes) the web browser userhas purchased (or would like to purchase) and which of the productcategories the web browser user likes.

FIGS. 12 and 13 provide screenshots of example graphical user interfaces1200 a, 1200 b, 1200 c, and 1200 d for accessing and interacting with auser advertisement preference system in accordance with someimplementations. In FIG. 12, the graphical user interface 1200 aillustrates a floating menu bar that can be presented at a client deviceby a client-side engine. Through the graphical user interfaces 1200 a,1200 b, 1200 c, and 1200 d, a web browser user can analyze (among otherthings) metrics relating to third parties that have access to the webbrowser user's user advertisement preferences. In FIG. 13, the graphicaluser interface 1300 illustrates a menu that can be presented at a clientdevice by a client-side engine and utilized by a web browser user toaccess their account settings.

As used herein, the term “set” may refer to any collection of elements,whether finite or infinite. The term subset may refer to any collectionof elements, wherein the elements are taken from a parent set; a subsetmay be the entire parent set. The term proper subset refers to a subsetcontaining fewer elements than the parent set.

As used herein, the term “implementation” means an implementation thatserves to illustrate by way of example but not limitation. Thetechniques described in the preceding text and figures can be mixed andmatched as circumstances demand to produce alternative implementations.

1. A method comprising: identifying, by a user advertisement preferencesystem, a user operating a web browser on a client device, the clientdevice including at least one processor, memory, the web browser, and aplugin in communication with the web browser, the client device beingremote from the user advertisement preference system; providing, by theuser advertisement preference system, the client device with a uniqueuser identifier associated with the user for a web browser cookie thatincludes the unique user identifier, the web browser cookie containingno user-related information including no user-identifying informationcapable of identifying the user to any online advertisement-providersystem, the web browser cookie being stored on the client device, theweb browser cookie configured to be provided from the client device to aweb server operating a web page that includes at least one onlineadvertisement request, the web server being remote from the clientdevice; receiving, by the user advertisement preference system, at leastone user advertisement preference specified by the user, the at leastone user advertisement preference indicating preferred or unpreferredadvertisements, the at least one user advertisement preference beingspecified by the user based on first user input received through a userinterface being displayed while an online advertisement is currentlybeing presented through the web browser, the user interface includingone or more questions related to the online advertisement, and the atleast one user advertisement preference being obtained from a responseto the one or more questions related to the online advertisement, theplugin configured to provide the at least one user advertisementpreference to the user advertisement preference system, the web browsercookie not being modified to contain the at least one user advertisementpreference; storing, by the user advertisement preference system, the atleast one user advertisement preference in association with the uniqueuser identifier; receiving, by the user advertisement preference system,a request from an online advertisement-provider system, the requestincluding the unique user identifier from the web browser cookie, theonline advertisement-provider system receiving the unique useridentifier from the web server, the at least one onlineadvertisement-provider system being remote from the user advertisementpreference system, remote from the web server, and remote from theclient device; retrieving, by the user advertisement preference system,the stored at least one user advertisement preference associated withthe unique user identifier; and providing, by the user advertisementpreference system, the stored at least one user advertisement preferenceto the online advertisement-provider system without providing anyuser-identifying information capable of identifying the user to the atleast one online advertisement-provider system, the at least one onlineadvertisement-provider system being capable of determining one or moreuser-targeted online advertisements to be presented to the user based atleast in part on the at least one user advertisement preference.
 2. Themethod of claim 1, wherein the receiving, by the user advertisementpreference system, the at least one user advertisement preferencespecified by the user includes receiving the at least one useradvertisement preference from the plugin on the client device, the atleast one user advertisement preference being specified in response to auser interface generated by the plugin in response to at least one firstonline advertisement presented to the user.
 3. The method of claim 2,wherein the at least one user advertisement preference indicates atleast one preference for or against advertisements that share one ormore characteristics with the at least one first online advertisement.4. The method of claim 3, wherein the one or more characteristicscorrespond to a product, a service, a product category, a servicecategory, a manufacturer, a service provider, a retailer, or price. 5.The method of claim 1, wherein the receiving, by the user advertisementpreference system, the at least one user advertisement preferencespecified by the user includes receiving the at least one useradvertisement preference from the plugin on the client device, the atleast one user advertisement preference being specified in response to auser interface generated by the plugin in response to selection by theuser of an icon in at least one first online advertisement presented tothe user.
 6. The method of claim 1, wherein the storing the at least oneuser advertisement preference in association with the unique useridentifier comprises storing the at least one user advertisementpreference in association with the user.
 7. The method of claim 1,further comprising requesting authorization, from the user, forproviding the at least one user advertisement preference to the onlineadvertisement-provider system.
 8. A user advertisement preferencesystem, comprising: one or more processors; memory storing instructionsthat, when executed by the one or more processors, cause the useradvertisement preference system to perform: identifying a user operatinga web browser on a client device, the client device including at leastone processor, memory, the web browser, and a plugin in communicationwith the web browser, the client device being remote from the useradvertisement preference system; providing the client device with aunique user identifier associated with the user for a web browser cookiethat includes the unique user identifier, the web browser cookiecontaining no user-related information including no user-identifyinginformation capable of identifying the user to any onlineadvertisement-provider system, the web browser cookie being stored onthe client device, the web browser cookie configured to be provided fromthe client device to a web server operating a web page that includes atleast one online advertisement request, the web server being remote fromthe client device; receiving at least one user advertisement preferencespecified by the user, the at least one user advertisement preferenceindicating preferred or unpreferred advertisements, the at least oneuser advertisement preference being specified by the user based on firstuser input received through a user interface being displayed while anonline advertisement is currently being presented through the webbrowser, the user interface including one or more questions related tothe online advertisement, and the at least one user advertisementpreference being obtained from a response to the one or more questionsrelated to the online advertisement, the plugin configured to providethe at least one user advertisement preference to the user advertisementpreference system, the web browser cookie not being modified to containthe at least one user advertisement preference; storing the at least oneuser advertisement preference in association with the unique useridentifier; receiving a request from an online advertisement-providersystem, the request including the unique user identifier from the webbrowser cookie, the online advertisement-provider system receiving theunique user identifier from the web server, the at least one onlineadvertisement-provider system being remote from the user advertisementpreference system, remote from the web server, and remote from theclient device; retrieving the stored at least one user advertisementpreference associated with the unique user identifier; and providing thestored at least one user advertisement preference to the onlineadvertisement-provider system without providing any user-identifyinginformation capable of identifying the user to the at least one onlineadvertisement-provider system, the at least one onlineadvertisement-provider system being capable of determining one or moreuser-targeted online advertisements to be presented to the user based atleast in part on the at least one user advertisement preference.
 9. Theuser advertisement preference system of claim 8, wherein theinstructions causing the user advertisement preference system to performreceiving the at least one user advertisement preference specified bythe user include instructions causing the user advertisement preferencesystem to perform receiving the at least one user advertisementpreference from the plugin on the client device, the at least one useradvertisement preference being specified in response to a user interfacegenerated by the plugin in response to at least one first onlineadvertisement presented to the user.
 10. The user advertisementpreference system of claim 9, wherein the at least one useradvertisement preference indicates at least one preference for oragainst advertisements that share one or more characteristics with theat least one first online advertisement.
 11. The user advertisementpreference system of claim 10, wherein the one or more characteristicscorrespond to a product, a service, a product category, a servicecategory, a manufacturer, a service provider, a retailer, or price. 12.The user advertisement preference system of claim 8, wherein theinstructions causing the user advertisement preference system to performreceiving the at least one user advertisement preference specified bythe user include instructions causing the user advertisement preferencesystem to perform receiving the at least one user advertisementpreference from the plugin on the client device, the at least one useradvertisement preference being specified in response to a user interfacegenerated by the plugin in response to selection by the user of an iconin at least one first online advertisement presented to the user. 13.The user advertisement preference system of claim 8, wherein theinstructions causing the user advertisement preference system to performstoring the at least one user advertisement preference in associationwith the unique user identifier include instructions causing the useradvertisement preference system to perform storing the at least one useradvertisement preference in association with the user.
 14. The useradvertisement preference system of claim 8, wherein the instructions,when executed by the one or more processors, further cause the useradvertisement preference system to perform requesting authorization,from the user, for providing the at least one user advertisementpreference to the online advertisement-provider system.